Description

1. Update orderbook::OrderExecuted event with the following data:

    #[derive(Drop, starknet::Event)]
    struct OrderExecuted {
        #[key]
        order_hash: felt252,
        #[key]
        order_status: OrderStatus,
        version: u8,
        transaction_hash: felt252,
        from: ContractAddress,
        to: ContractAddress,
    }

2. Update diri to handle OrderExecuted version 0 and version 1

What type of PR is this? (check all applicable)

• 🍕 Feature (feat:)
• 🐛 Bug Fix (fix:)
• 📝 Documentation Update (docs:)
• 🎨 Style (style:)
• 🧑‍💻 Code Refactor (refactor:)
• 🔥 Performance Improvements (perf:)
• ✅ Test (test:)
• 🤖 Build (build:)
• 🔁 CI (ci:)
• 📦 Chore (chore:)
• ⏩ Revert (revert:)
• 🚀 Breaking Changes (BREAKING CHANGE:)

Related Tickets & Documents

Added tests?

• 👍 yes
• 🙅 no, because they aren't needed
• 🙋 no, because I need help

Added to documentation?

• 📜 README.md
• 📓 Documentation
• 🙅 no documentation needed

[optional] Are there any post-deployment tasks we need to perform?

[optional] What gif best describes this PR or how it makes you feel?

PR Title and Description Guidelines:

• Ensure your PR title follows semantic versioning standards. This helps automate releases and changelogs.
• Use types like feat:, fix:, chore:, BREAKING CHANGE: etc. in your PR title.
• Your PR title will be used as a commit message when merging. Make sure it adheres to Conventional Commits standards.

Closing Issues